Repository navigation
fix: keep full soup food on every scoop - #33
Conversation
Ladling a pot was splitting the soup template food by the serving count, so each bowl was only a fraction of the dish. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughSoup scooping now uses the template food value unchanged. The ChangesSoup scoop food value
Estimated code review effort: 2 (Simple) | ~5 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to Each soup serving retains the template food value through consumption, subject to the usual quality and nutrition modifiers. No material merge risk was identified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
Summary
pot-soup-scoops. Each bowl keeps the soup template food (26), and nutrition stays at the template level.Documentation impact
Contract
mvn test, or why not):mvn -Dtest=PortionRulesTest,ValuableIngredientTest testProvinceSystem/wiki/cookingor related pages): no changeNotes
src/main/resources. Do not edittarget/.plugin.ymlversion andpom.xmlversion are known drift. Do not mix a version bump into unrelated work.cookware.ymlis not loaded.Made with Cursor
Summary by CodeRabbit